LogDoor User's Guide

As a general troubleshooting hint, remember that a LogDoor task's output is always derived from that task's input log file. If something goes wrong with the processing, you can always start the processing over from the beginning (as described in the LogDoor Files section). Although doing so may take some time, you can never lose any data as long as you keep the original log file around.

• Check the display to make sure that LogDoor has processed all of the current input file. If the "Processed" line indicates less then 100% of the input file has been processed, you need to wait for LogDoor to process the rest of the log file.
  

• Check the access popup at the top of the site-by-site display to ensure that it is set as desired. Also check your Macintosh's clock to be sure that it is set to the correct date and time.
  

• Be sure the task is in run mode. If the task is suspended, it will not update the status window display.
  

• If your Web server is actively writing to the log file, LogDoor will only be able to open that file if it is running on the same Macintosh as your Web server. LogDoor can not open active log files over the network.
  

• Check to be sure that some other application does not have the file open for exclusive access.
  

• Check to make sure that the log file has not been deleted or moved to another disk.
  

• You cannot move a task file from one Mac to another without reselecting the input file.
  

• Check to make sure that the disk to which LogDoor is writing its output is not full or write-protected.
  

• Be sure the file has not been opened by some other application.
  

• Check to make sure the output log files have been selected in the Output Files dialog box.
  

• Make sure that the selected output folder is where you think it is by looking at the Output Files dialog box.
  

• Check to make sure the output log summary reports have been selected in the Output Files dialog box.
  

• Check to be sure that you have enabled the periodic writing of summary reports in the Scheduling dialog box.
  

• Check to make sure that there is not an alias for that site in the output folder, with that alias pointing to somewhere other than where you expect these files to go.
  

• If all accesses to the site produce errors (ERR! log lines), no logs or reports will be created for that site, as indicated in the section on LogDoor's output files. The information will be written to the "Root" output folder instead.
  

• Remember that LogDoor writes out all error entries for sites which it has not previously encountered to files in the root folder.
  

• You may want to configure your Web server to transfer log files with a custom MIME type. See Appendix 1 for details.
  

• The summary reports reflect the processing performed to date by a particular task. If that task has ever performed processing which it output to different output log files, or to no log files at all, then the summary information will not match with the information in the output log.
  

• Information could have been output to the log file by another task in addition to the current one.
  

• If the task's summary data was ever reset, the summary information will not match with the output logs.
  

• Under rare conditions, due to crashes or unexpected shutdown of the Macintosh on which LogDoor is running, some data could be written to the output log but not stored in the task's processing state, or vice versa.
  

• If you are running WebSTAR, check to make sure that the first line in WebSTAR's output log is a formatting line (beginning with !!). If not, especially if you have changed your log file format from the default, it is possible that LogDoor can not correctly determine the format of the log file. You may wish to manually add a formatting line to the start of your log file, using a text editor. The structure of a formatting line is described in the WebSTAR reference manual.
  

• If you move the Output folder while a task is running, a new output folder will be created whenever a new site is processed.
  

• Check the Output files lines in the task status window to make sure the desired output folder is selected.